<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN""http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="zh" xml:lang="zh" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<head>
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Task Descriptor: Assess and Improve Test Effort</title>
<meta name="uma.type" content="TaskDescriptor">
<meta name="uma.name" content="assess_improve_test_effort">
<meta name="uma.presentationName" content="Assess and Improve Test Effort">
<meta name="uma.guid" content="_kwkTgEoiEdqrjq4i3fchvA">
<meta name="element_type" content="TaskDescriptor">
<meta name="filetype" content="description">
<meta name="role" content="">
<link rel="StyleSheet" href="./../../css/default.css" type="text/css">
<script src="./../../scripts/ContentPageResource.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/ContentPageSection.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/ContentPageSubSection.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/ActivityTreeTable.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/ProcessElementPage.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/ContentPageToolbar.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/contentPage.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/processElementData.js" type="text/javascript" language="JavaScript"></script><script type="text/javascript" language="JavaScript">
					var defaultQueryStr = '?proc={35359DDF-6361-43E5-8B1B-18D204DA8CFF}&path={35359DDF-6361-43E5-8B1B-18D204DA8CFF},{5DA9C9E9-1538-4433-8B57-B28667D67514},_kwkTgEoiEdqrjq4i3fchvA';
					var backPath = './../../';
					var imgPath = './../../images/';
					var nodeInfo=null;
					contentPage.preload(imgPath, backPath, nodeInfo, defaultQueryStr, true, true, false);
				</script>
</head>
<body>
<div id="breadcrumbs"></div>
<table border="0" cellpadding="0" cellspacing="0" width="100%">
<tr>
<td valign="top">
<div id="page-guid" value="_kwkTgEoiEdqrjq4i3fchvA"></div>
<table border="0" cellspacing="0" cellpadding="0" width="100%">
<tr>
<td class="pageTitle" nowrap="true">Task Descriptor: Assess and Improve Test Effort</td><td width="100%">
<div align="right" id="contentPageToolbar"></div>
</td><td width="100%" class="expandCollapseLink" align="right"><a name="mainIndex" href="./../../index.htm"></a><script language="JavaScript" type="text/javascript" src="./../../scripts/treebrowser.js"></script></td>
</tr>
</table>
<table width="100%" border="0" cellpadding="0" cellspacing="0">
<tr>
<td class="pageTitleSeparator"><img src="./../../images/shim.gif" alt="" title="" height="1"></td>
</tr>
</table>
<div class="overview">
<table width="97%" border="0" cellspacing="0" cellpadding="0">
<tr>
<td width="50"><img src="./../../images/taskdes_lg_dgm32.gif" alt="" title=""></td><td>
<table class="overviewTable" border="0" cellspacing="0" cellpadding="0">
<tr>
<td valign="top">This task focuses on making timely changes to the test effort in order to increase its effectiveness.</td>
</tr>
<tr>
<td>Based on Method Task: <a href="./../../rup/tasks/assess_improve_test_effort_420E74C2.html" guid="{AE6717A4-5E8C-41B6-8460-B743C9BDB437}">Assess and Improve Test Effort</a></td>
</tr>
</table>
</td>
</tr>
</table>
</div>
<div class="sectionHeading">Relationships</div>
<div class="sectionContent">
<table class="sectionTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<th class="sectionTableHeading" scope="row">Roles</th><td class="sectionTableCell" width="30%"><span class="sectionTableCellHeading">Main:
								</span>
<ul>
<li>
<a href="./../../rup/capabilitypatterns/rup_test_manager_91449E26.html" guid="_CXJIURi2Edq_uI8xTPML6g">测试管理员</a>
</li>
</ul>
</td><td class="sectionTableCell" width="30%"><span class="sectionTableCellHeading">Additional:
								</span></td><td class="sectionTableCell"><span class="sectionTableCellHeading">Assisting:
								</span></td>
</tr>
<tr valign="top">
<th class="sectionTableHeading" scope="row">Inputs</th><td class="sectionTableCell" width="30%"><span class="sectionTableCellHeading">Mandatory:
								</span>
<ul>
<li>
<a href="./../../rup/capabilitypatterns/rup_test_plan_BED99930.html" guid="_kwqaIEoiEdqrjq4i3fchvA">测试计划</a>
</li>
<li>
<a href="./../../rup/capabilitypatterns/rup_test_evaluation_summary_8A7B924C.html" guid="_CXJIUxi2Edq_uI8xTPML6g">测试评估摘要</a>
</li>
<li>
<a href="./../../rup/capabilitypatterns/rup_iteration_plan_7FDDB23C.html" guid="_CXJIUhi2Edq_uI8xTPML6g">迭代计划</a>
</li>
</ul>
</td><td class="sectionTableCell" width="30%"><span class="sectionTableCellHeading">Optional:
								</span>
<ul>
<li>
<a href="./../../rup/capabilitypatterns/rup_change_request_C9777940.html" guid="_kwqaIUoiEdqrjq4i3fchvA">变更请求</a>
</li>
<li>
<a href="./../../rup/capabilitypatterns/rup_test_results_446F945B.html" guid="_CXJIVhi2Edq_uI8xTPML6g">测试结果 </a>
</li>
<li>
<a href="./../../rup/capabilitypatterns/rup_iteration_assessment_B8108D56.html" guid="_kwqaIkoiEdqrjq4i3fchvA">迭代评估</a>
</li>
<li>
<a href="./../../rup/capabilitypatterns/rup_review_record_836B7B4F.html" guid="_kwqaJEoiEdqrjq4i3fchvA">评审记录</a>
</li>
<li>
<a href="./../../rup/capabilitypatterns/rup_project_measurements_4F0D746B.html" guid="_CXJIVxi2Edq_uI8xTPML6g">项目评估</a>
</li>
<li>
<a href="./../../rup/capabilitypatterns/rup_quality_assurance_plan_55D68045.html" guid="_CXJIVRi2Edq_uI8xTPML6g">质量保证计划</a>
</li>
<li>
<a href="./../../rup/capabilitypatterns/rup_status_assessment_20EA631B.html" guid="_kwqaI0oiEdqrjq4i3fchvA">状态评估</a>
</li>
</ul>
</td><td class="sectionTableCell"><span class="sectionTableCellHeading">External:
								</span>
<ul>
<li>None</li>
</ul>
</td>
</tr>
<tr valign="top">
<th class="sectionTableHeading" scope="row">Outputs</th><td class="sectionTableCell" colspan="3">
<ul>
<li>
<a href="./../../rup/capabilitypatterns/rup_test_plan_BED99930.html" guid="_kwqaIEoiEdqrjq4i3fchvA">测试计划</a>
</li>
<li>
<a href="./../../rup/capabilitypatterns/rup_test_evaluation_summary_8A7B924C.html" guid="_CXJIUxi2Edq_uI8xTPML6g">测试评估摘要</a>
</li>
</ul>
</td>
</tr>
</table>
</div>
<div class="sectionHeading">Steps</div>
<div class="sectionContent">
<table class="sectionTable" border="0" cellspacing="0" cellpadding="0">
<tr>
<td class="sectionTableCell">
<div class="stepHeading"> Capture work status </div>
<div class="stepContent">
<table class="stepTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<td><a id="CaptureWorkStatus" name="CaptureWorkStatus"></a>
<div align="left">
    <table border="1" width="100%" cellspacing="0" cellpadding="4" style="border: 1px solid rgb(128,128,128)"     bordercolorlight="#808080" bordercolordark="#808080">
        <tr>
            <td width="5%">
                <b>Purpose:</b>&nbsp;
            </td>
            <td width="95%">
                To gain an objective, up-to-date understanding of the general status of the testing work against
                plan.&nbsp;
            </td>
        </tr>
    </table><br />
</div>
<p>
    There are different ways to approach this step, and much of the approach will depend on your project culture. Where
    available, gather and collate progress reports prepared by individual team members or sub-teams. Project time sheets
    are another possible source to consider. Where project scheduling systems such as Microsoft Project are actively used
    and updated with actual progress this provides another useful information source. Where available and actively used,
    you might also derive objective status or progress metrics from configuration and change management systems.
</p>
<p>
    For this step and subsequent steps that deal with gathering information and assessing the test effort, try to obtain a
    balanced view incorporating both objective and subjective measures. Remember that objective numbers only give part of
    the picture and need to be supported and explained by the current project "climate". Conversely, don't rely purely on
    hearsay and subjective speculation about the test effort: look for supporting objective evidence. We recommend you
    supplement your objective data by discussion with either team leads or where possible individual team members to gather
    subjective assessments and gauge how much confidence you can place in the objective data.
</p></td>
</tr>
</table>
</div>
<div class="stepHeading"> Gather test effort productivity and effectiveness metrics </div>
<div class="stepContent">
<table class="stepTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<td><a id="GatherTestProductEffectMetrics" name="GatherTestProductEffectMetrics"></a>
<div align="left">
    <table border="1" width="100%" cellspacing="0" cellpadding="4" style="border: 1px solid rgb(128,128,128)"     bordercolorlight="#808080" bordercolordark="#808080">
        <tr>
            <td width="5%">
                <b>Purpose:</b>&nbsp;
            </td>
            <td width="95%">
                To gather and examine objective data that enables the assessment of the testing performed by the test
                team.&nbsp;
            </td>
        </tr>
    </table><br />
</div>
<p>
    Investigate how much effort has been spent on the identification, definition, design, implementation and execution of
    tests. Keep an eye out for signs of excessive effort being devoted to one aspect of the test effort to the detriment of
    others. Look also for areas where effort may be unproductive or not showing sufficient benefit for the level of effort
    being expended.
</p>
<p>
    Look also at the effectiveness of the testing. Look for data that supports your initial observations of effectiveness.
    Consider aspects such as defect discovery rate, defect severity counts, duplicate defect statistics, and defects
    detected as test escapes.
</p></td>
</tr>
</table>
</div>
<div class="stepHeading"> Gather Change Request distribution, trend and aging metrics </div>
<div class="stepContent">
<table class="stepTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<td><a id="CRMetrics" name="CRMetrics"></a>
<div align="left">
    <table border="1" width="100%" cellspacing="0" cellpadding="4" style="border: 1px solid rgb(128,128,128)"     bordercolorlight="#808080" bordercolordark="#808080">
        <tr>
            <td width="5%">
                <b>Purpose:</b>&nbsp;
            </td>
            <td width="95%">
                To gather and examine objective data that enables the assessment of the issues and defects logged by the
                test team.&nbsp;
            </td>
        </tr>
    </table><br />
</div>
<p>
    Identify important trends evident in the Change Request data. In general it's less important for this task to spend
    time analyzing data volumes and more important to identify what the relative data trends are indicating. Look for
    positive signs such as a steady, continuous rate of defect discovery, or a light ongoing increase or decrease in
    discovery rate over time. Be on the lookout for sharp peaks and troughs in discovery rate that indicate the test team
    may be encountering process, environmental, political or other problems that are reducing their productivity.
</p>
<p>
    Look at trends in defects closures. Look for significant increases of closures by development staff as "not
    reproducible"; identify cases where this is a result of insufficient analysis of the failure having been performed by
    the test team and quantify the extent of this problem. Look at trends in defects being closed by development staff as
    "functioning as designed"; identify cases where this is a result of insufficient analysis of the specification having
    been performed by the test team and quantify the extent of this problem. Be careful to confirm these indications are
    not false and due instead to overworked developers triaging their workload. Some analysis should also be done of defect
    verification trends as fixes to defects are released to the test team in subsequent builds: look out for trends that
    indicate defects awaiting verification by the test team are aging or growing to an unmanageable number.
</p>
<p>
    Look for other trends that indicate problems. Look at the the way in which defects and other change requests have been
    recorded or managed by the test team: ambiguous and insufficient information on a change request is difficult and
    frustrating for a developer to take action on. The team should take care to monitor that the quality of the information
    recorded against defects remains-on average-relatively high. Take the opportunity to improve the clarity of the
    associated Change Requests, eliminating ambiguity and emotive language and reasoning. Work together with the
    individuals who created these work products to ensure the essence of the problem is clearly stated and encourage them
    to find factual and accurate ways to approach discussing the Issues.
</p>
<p>
    Also look out for imbalances in defect distribution on a number of different dimensions. Look for functional areas of
    the application or the specification that have low defect counts raised against them: this may indicate an exposure
    that insufficient testing has been undertaken in that functional area. Look also at distribution by test team member:
    there may be indications that individual team members are overworked and that productivity is suffering.
</p></td>
</tr>
</table>
</div>
<div class="stepHeading"> Gather traceability, coverage and dependency metrics </div>
<div class="stepContent">
<table class="stepTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<td><a id="GatherTraceability" name="GatherTraceability"></a>
<div align="left">
    <table border="1" width="100%" cellspacing="0" cellpadding="4" style="border: 1px solid rgb(128,128,128)"     bordercolorlight="#808080" bordercolordark="#808080">
        <tr>
            <td width="5%">
                <b>Purpose:</b>&nbsp;
            </td>
            <td width="95%">
                To gather and examine objective data that enables the assessment asset traceability.&nbsp;
            </td>
        </tr>
    </table><br />
</div>
<p>
    Analyze the state of the traceability relationships between the testing assets-Test Ideas, Test Cases, Test Scripts,
    Test Suites and Change Requests-and the upstream and downstream assets they relate to. Look for signs that indicate the
    test effort is focused on the correct areas and a useful set of motivations. Look also for negative indications that
    suggest certain aspects of testing are missing or are no longer of importance: If the requirements or development teams
    are working on areas not represented by the current test effort, this should raise concerns.
</p></td>
</tr>
</table>
</div>
<div class="stepHeading"> Evaluate metrics and formulate initial assessment </div>
<div class="stepContent">
<table class="stepTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<td><a id="EvaluateMetrics" name="EvaluateMetrics"></a>
<div align="left">
    <table border="1" width="100%" cellspacing="0" cellpadding="4" style="border: 1px solid rgb(128,128,128)"     bordercolorlight="#808080" bordercolordark="#808080">
        <tr>
            <td width="5%">
                <b>Purpose:</b>&nbsp;
            </td>
            <td width="95%">
                To evaluate and assess the metric data and formulate an initial assessment of the effectiveness of the test
                effort against plan.&nbsp;
            </td>
        </tr>
    </table><br />
</div>
<p>
    Collate all of the information you have gathered and evaluate it as a collective whole. Remember that each piece of the
    data gathered only addresses one aspect of the total assessment, and you must formulate your assessment of the test
    effort based on a balanced and considered view of all data.
</p>
<p>
    Record you initial assessment in a format that will be suitable for the stakeholders to make comments and give feedback
    on.
</p></td>
</tr>
</table>
</div>
<div class="stepHeading"> Record findings </div>
<div class="stepContent">
<table class="stepTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<td><a id="RecordFindings" name="RecordFindings"></a>
<div align="left">
    <table border="1" width="100%" cellspacing="0" cellpadding="4" style="border: 1px solid rgb(128,128,128)"     bordercolorlight="#808080" bordercolordark="#808080">
        <tr>
            <td width="5%">
                <b>Purpose:</b>&nbsp;
            </td>
            <td width="95%">
                To document summary findings for inclusion in project management reporting and to enable analysis of
                subsequent status assessment against earlier assessments.&nbsp;
            </td>
        </tr>
    </table><br />
</div>
<p>
    This task produces summary status information that is important to the project manager and other roles in the
    management team. These roles will use the summary findings to make informed decisions about the project.
</p>
<p>
    We recommend your record some aspects of the test effort assessment in a format that allows subsequent assessments to
    be compared and contrasted with previous ones. This will enable you to analyze the relative trend in test effort
    improvements over time.
</p></td>
</tr>
</table>
</div>
<div class="stepHeading"> Present assessment and gather feedback </div>
<div class="stepContent">
<table class="stepTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<td><a id="PresentAssessment" name="PresentAssessment"></a>
<div align="left">
    <table border="1" width="100%" cellspacing="0" cellpadding="4" style="border: 1px solid rgb(128,128,128)"     bordercolorlight="#808080" bordercolordark="#808080">
        <tr>
            <td width="5%">
                <b>Purpose:</b>&nbsp;
            </td>
            <td width="95%">
                To engage stakeholders and obtain their feedback on whether the actual testing effort is serving their
                needs.&nbsp;
            </td>
        </tr>
    </table><br />
</div>
<p>
    Present your assessment for stakeholders to comment and offer feedback on. The format or method for doing this will
    differ from project to project: in some cases it will be a series of informal conversations, in another simply a
    posting on a project intranet web-site, and in others a formal presentation-choose a format that suits your culture.
</p>
<p>
    Even with the best planning and specification documents possible, there will usually be differences between the
    original expectation and intent of those documents and the resulting end product. This is as true for testing and
    evaluating software as it is for the software development itself. The value of this step is to take the opportunity to
    elicit the stakeholders feedback and identify where the careful planning and documentation has not achieved what was
    originally expected or intended.
</p></td>
</tr>
</table>
</div>
<div class="stepHeading"> Plan and implement improvement initiatives </div>
<div class="stepContent">
<table class="stepTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<td><a id="ImplementImprovements" name="ImplementImprovements"></a>
<div align="left">
    <table border="1" width="100%" cellspacing="0" cellpadding="4" style="border: 1px solid rgb(128,128,128)"     bordercolorlight="#808080" bordercolordark="#808080">
        <tr>
            <td width="5%">
                <b>Purpose:</b>&nbsp;
            </td>
            <td width="95%">
                To identify areas for improvement and formulate initial strategies for achieving those improvements.&nbsp;
            </td>
        </tr>
    </table><br />
</div>
<p>
    Based on your analysis and the feedback you've received from various stakeholders, identify opportunities for
    improvement. Look for ways to make the testing more effective, productive and efficient. This might involve:
    reassigning staff, including pairing staff to work more effectively or employing specialized contractors; using
    productivity tools to improve efficiency; finding alternative approaches and techniques that are more productive in
    terms of finding defects.
</p>
<p>
    In most cases it's better to make small, incremental improvements to the test effort and avoid the risk of derailing
    the project with large, unsettling changes: In some cases a bigger change is warranted and useful. Use your best
    judgment to formulate an appropriate approach to improvement and discuss your ideas with other management staff to get
    their input before committing the team to embrace large changes.
</p></td>
</tr>
</table>
</div>
<div class="stepHeading"> Monitor and support improvement initiatives </div>
<div class="stepContent">
<table class="stepTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<td><a id="ManageImprovements" name="ManageImprovements"></a>
<div align="left">
    <table border="1" width="100%" cellspacing="0" cellpadding="4" style="border: 1px solid rgb(128,128,128)"     bordercolorlight="#808080" bordercolordark="#808080">
        <tr>
            <td width="5%">
                <b>Purpose:</b>&nbsp;
            </td>
            <td width="95%">
                To ensure that necessary improvement initiatives are achieved in a satisfactory and timely manner.&nbsp;
            </td>
        </tr>
    </table><br />
</div>
<p>
    For the improvements to be effective, you will need to manage their success. Identify ways that you will be able to
    monitor improvement initiatives-preferably in advance on their adoption-to assess their effectiveness. Either actively
    monitor the progress being made in adopting the changes yourself, or appoint someone else on the team to do so.
</p>
<p>
    Most changes meet resistance or problems that must be overcome for them to be ultimately successful. Allow time for and
    be prepared to quickly address any issues that arise and prevent the initiative from succeeding. Be sensitive to
    peoples natural reluctance to change and find ways to address their concerns appropriately.
</p></td>
</tr>
</table>
</div>
<div class="stepHeading"> Evaluate and verify your results </div>
<div class="stepContent">
<table class="stepTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<td><a id="EvaluateResults" name="EvaluateResults"></a>
<div align="left">
    <table border="1" width="100%" cellspacing="0" cellpadding="4" style="border: 1px solid rgb(128,128,128)"     bordercolorlight="#808080" bordercolordark="#808080">
        <tr>
            <td width="5%">
                <b>Purpose:</b>&nbsp;
            </td>
            <td width="95%">
                To verify that the task has been completed appropriately and that the resulting work products are
                acceptable.&nbsp;
            </td>
        </tr>
    </table><br />
</div>
<p>
    Now that you have completed the work, it is beneficial to verify that the work was of sufficient value, and that you
    did not simply consume vast quantities of paper. You should evaluate whether your work is of appropriate quality, and
    that it is complete enough to be useful to those team members who will make subsequent use of it as input to their
    work. Where possible, use the checklists provided in NUP to verify that quality and completeness are "good enough".
</p>
<p>
    Have the people performing the downstream tasks that rely on your work as input take part in reviewing your interim
    work. Do this while you still have time available to take action to address their concerns. You should also evaluate
    your work against the key input work products to make sure you have represented them accurately and sufficiently. It
    may be useful to have the author of the input work product review your work on this basis.
</p>
<p>
    Try to remember that that NUP is an iterative delivery process and that in many cases work products evolve over time.
    As such, it is not usually necessary-and is often counterproductive-to fully-form a work product that will only be
    partially used or will not be used at all in immediately subsequent work. This is because there is a high probability
    that the situation surrounding the work product will change-and the assumptions made when the work product was created
    proven incorrect-before the work product is used, resulting in wasted effort and costly rework. Also avoid the trap of
    spending too many cycles on presentation to the detriment of content value. In project environments where presentation
    has importance and economic value as a project deliverable, you might want to consider using an administrative resource
    to perform presentation tasks.
</p><br />
<br /></td>
</tr>
</table>
</div>
</td>
</tr>
</table>
</div>
<div class="sectionHeading">Properties</div>
<div class="sectionContent">
<table class="sectionTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<th class="sectionTableHeading" scope="row" id="property_Multiple Occurrences" abbr="Multiple Occurrences">Multiple Occurrences</th><td class="sectionTableCell" align="left" headers="property_Multiple Occurrences"><img width="20" height="15" alt="" title="" src="./../../images/indent.gif"></td>
</tr>
<tr valign="top">
<th class="sectionTableHeading" scope="row" id="property_Event Driven" abbr="Event Driven">Event Driven</th><td class="sectionTableCell" align="left" headers="property_Event Driven"><img width="20" height="15" alt="" title="" src="./../../images/indent.gif"></td>
</tr>
<tr valign="top">
<th class="sectionTableHeading" scope="row" id="property_Ongoing" abbr="Ongoing">Ongoing</th><td class="sectionTableCell" align="left" headers="property_Ongoing"><img width="20" height="15" alt="" title="" src="./../../images/indent.gif"></td>
</tr>
<tr valign="top">
<th class="sectionTableHeading" scope="row" id="property_Optional" abbr="Optional">Optional</th><td class="sectionTableCell" align="left" headers="property_Optional"><img width="20" height="15" alt="" title="" src="./../../images/indent.gif"></td>
</tr>
<tr valign="top">
<th class="sectionTableHeading" scope="row" id="property_Planned" abbr="Planned">Planned</th><td class="sectionTableCell" align="left" headers="property_Planned"><img width="20" height="15" alt="" title="" src="./../../images/indent.gif"></td>
</tr>
<tr valign="top">
<th class="sectionTableHeading" scope="row" id="property_Repeatable" abbr="Repeatable">Repeatable</th><td class="sectionTableCell" align="left" headers="property_Repeatable"><img width="20" height="15" alt="" title="" src="./../../images/indent.gif"></td>
</tr>
</table>
</div>
<table class="copyright" border="0" cellspacing="0" cellpadding="0">
<tr>
<td class="copyright">Copyright &copy; 2008 版权所有 东软集团股份有限公司&nbsp; 联系邮箱:<a href="mailto:tcoe@neusoft.com">tcoe@neusoft.com</a></td>
</tr>
</table>
</td>
</tr>
</table>
</body>
<script language="JavaScript" type="text/javascript">
					contentPage.onload();
					contentPage.processPage.fixDescriptorLinks();
				</script>
</html>
